Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: clone sig metadata properties #4316

Closed
wants to merge 1 commit into from

Conversation

rscampos
Copy link
Contributor

@rscampos rscampos commented Sep 20, 2024

fix: #4298
fix: #4313

1. Explain what the PR does

0b164b1 fix: clone sig metadata properties

2. Explain how to test it

3. Other comments

Copy link
Member

@geyslan geyslan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Put some wondering.

go.mod Outdated Show resolved Hide resolved
signatures/helpers/helpers.go Outdated Show resolved Hide resolved
@geyslan
Copy link
Member

geyslan commented Sep 20, 2024

This issue's impacting latest docker images. So we should release a new minor after merging and testing.

Copy link
Member

@geyslan geyslan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@NDStrahilevitz
Copy link
Collaborator

Forgive me for asking, but are we any better off now than the original version where the function just returned the metadata as a struct? So maybe we have now (at best) (mem footprint)=original-(no copy)+(clone the properties).
But we lost ease of authoring and readability which are in the context of signatures more important IMO.

@rscampos
Copy link
Contributor Author

I think you’re right, @NDStrahilevitz. Initially, we saw a performance improvement, but then an issue arose. After discussing it with @geyslan, we’re considering a rollback. Thanks!

@geyslan
Copy link
Member

geyslan commented Sep 24, 2024

We're already reverted related changes.

@geyslan geyslan closed this Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants